docs: Mention Window::close-request in the migration guide
authorEmmanuele Bassi <ebassi@gnome.org>
Wed, 9 Jun 2021 17:03:12 +0000 (18:03 +0100)
committerEmmanuele Bassi <ebassi@gnome.org>
Wed, 9 Jun 2021 17:03:12 +0000 (18:03 +0100)
The Widget::delete-event signal was moved to Window::close-request.

docs/reference/gtk/migrating-3to4.md

index 9bc982962ae71e3a95a2c05ea80435c7b8d5e9c4..49f3d6c8ddd2bd78ee14974cccf447ee67c0ed91 100644 (file)
@@ -187,11 +187,16 @@ for this change.
 | ::grab-broken-event | - |
 
 Event signals which are not directly related to input have to be dealt with
-on a one-by-one basis. If you were using `::configure-event` and
-`::window-state-event` to save window state, you should use property
-notification for corresponding [class@Gtk.Window] properties, such as
-[property@Gtk.Window:default-width], [property@Gtk.Window:default-height],
-[property@Gtk.Window:maximized] or [property@Gtk.Window:fullscreened].
+on a one-by-one basis:
+
+ - If you were using `::configure-event` and `::window-state-event` to save
+   window state, you should use property notification for corresponding
+   [class@Gtk.Window] properties, such as [property@Gtk.Window:default-width],
+   [property@Gtk.Window:default-height], [property@Gtk.Window:maximized] or
+   [property@Gtk.Window:fullscreened].
+ - If you were using `::delete-event` to present a confirmation when using
+   the close button of a window, you should use the
+   [signal@Gtk.Window::close-request] signal.
 
 ### Set a proper application ID